Release 10.1A: OpenEdge Application Server:
Developing AppServer Applications

Connecting directly to an AppServer

Connecting directly to an AppServer without a NameServer is desirable if the configuration for your application is simple and static and, as a result, you do not need location transparency or load balancing. For these configurations, not taking advantage of the optional NameServer means having less to configure and manage.

Connecting directly to an AppServer also eliminates conflicts that might arise when you do not want to use the User Datagram Protocol (UDP) that the NameServer uses. If you have restrictions that prohibit using UDP, you can connect directly to an AppServer to avoid these restrictions.

This is the URL syntax for connecting directly to an AppServer (or BrokerConnect) over an intranet using the AppServer protocol (ignore line breaks):

Syntax

{AppServerDC:|AppServerDCS:}[//AppServer-host][:AppServer-port]/ [AppService-name]

AppServerDC

The client connects directly to the AppServer.

AppServerDCS

The client connects directly to an SSL-enabled AppServer as an SSL client. For more information on using an SSL-enabled AppServer, see the sections on using SSL in Chapter 4, " Design and Implementation Considerations."

AppServer-host

AppServer TCP/IP host address or host name that holds the service.

AppServer-port

AppServer TCP/IP port address for the AppServer specified with AppServer-host.

AppService-name

Name of the application service (AppServer or BrokerConnect).

For example, the following three URLs perform a direct TCP/IP connection to a shipping dock AppServer service or a salary management service. In the first example, the AppServer service is located at the default TCP/IP port, 3090; in the second, at a non-standard TCI/IP port, 3651; and in the third, an SSL connection is established, as shown:

AppServerDC://dbserver/shippingService AppServerDC://dbserver:3651/shippingService AppServerDCS://dbserver/salaryService